Removing 'Notes Single Logon' during client upgrade

HCL Notes/Domino 8.5 Forum (includes Notes Traveler)

Subject: Removing 'Notes Single Logon' during client upgrade

Feedback Type: Question

Product Area: Notes Client

Technical Area: Administration

Platform: Windows

Release: 8.5.3

Reproducible: Not applicable

We are about to roll out an 8.5.3 client upgrade across an organization that has a range of client versions.

They also have 'Notes Single Logon' installed on every client. We would like to replace that with the more recent 'Notes Shared Login' (yeah, trying explaining THAT to a client administrator - two different technologies with the same acronym!).

The policies and policy settings are in place, and have been applied across the board. Obviously the new settings will not take precedence until the older NSL has been de-activated (the two cannot co-exist).

So, I'd very much like to clarify exactly how I make this upgrade as seamless as possible so that the users observe no disruption to their ability to log in to Lotus Notes using their Windows password.

Since the policy settings have been established and have been applied, is it simply a matter of adding 'SINGLE_LOGON_INSTALLED_TURNOFF=1' to the users' NOTES.INI files prior to the upgrade?

The way I read it (http://www-01.ibm.com/support/docview.wss?uid=swg21367208), this should automate the de-activation of 'Notes Single Logon' during the upgrade so that 'Notes Shared Login' will take immediate effect upon restarting the Lotus Notes client.

Is this true, or is there something else I need to consider to ensure the older NSL is de-activated and the more recent NSL is activated all at the same time?

Cheers!

T.

Feedback number WEBB8REVE8 created by ~Wei Asatoopulakol on 02/12/2012

Status: Open
Comments: